Date: Tue, 6 Sep 94 04:30:02 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.Edu Reply-To: TCP-Group@UCSD.Edu Precedence: Bulk Subject: TCP-Group Digest V94 #195 To: tcp-group-digest TCP-Group Digest Tue, 6 Sep 94 Volume 94 : Issue 195 Today's Topics: Compiling jnos110g KA9Q NOS as router Linux resolver problem Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Mon, 05 Sep 94 16:00:43 PST From: kg7hq@techcenter.paccar.com (Michael A. Sterba) Subject: Compiling jnos110g To: tcp-group@ucsd.edu KG7HQ - OES SKAGIT CO. WA. Internet/ampr.org Mail Link X-Mailer: PCElm 3.21 Hello all, I'm going to show to all that I'm new in the area. I'm trying to compile jnos110g from it's source code I downloaded from ftp.ucsd. I tried borland tc2 and tc+ version3.0 with no success. I know enough to modify the makefile and select the correct directories in the above. But, no matter what version I use, I getting command syntax errors starting with line 153. It never makes it to the compiling stage of things. Has anyone else run into this scenerio?? I'm running a 486sx and have most of the 640k free for the above. I should have enough disk space with 85megs free. Thanks ahead of time........ Michael A. Sterba ³ AX25 Mail.........KG7HQ @ N7RHQ.#NWWA.WA.USA.NA [44.24.112.28] ³ Ham TCP/IP........kg7hq@kg7hq.ampr.org [160.69.38.12] ³ Internet..........kg7hq@techcenter.paccar.com ------------------------------ Date: Mon, 5 Sep 94 15:56:01 GMT From: "William Allen Simpson" Subject: KA9Q NOS as router To: tcp-group@ucsd.edu > From: jmorriso@bogomips.ee.ubc.ca (John Paul Morrison) > NOS is only being used as a router. (OK, maybe it's not a UDP thing. > Come to think of it, NOS has crashed when I've done ftp's *through* > the NOS router to other machines) > > > My NOS router at home stays up for months at a time, despite heavy > > daily use (from my BSDI box) for just about every protocol in the > > suite - Telnet, FTP, rlogin, X, NFS, DNS, NNTP, SMTP, you name it. > > run xmaze and one/both of the NOS routers crashes. > ... > I wanted to route TCP/IP from an ethernet to an arcnet network. > I tried NOS. It would stop routing after a day or two. It would > crash depending on what version of NCSA people used on the arcnet > PCs to ftp from the Suns. So I installed PCRoute, and it's run for > years, only rebooting due to the power failures on campus. > 1) please identify which "flavor" of NOS you are using. 2) KA9Q NOS is used as a base for a number of commercial routers. They wouldn't sell if they crashed a lot. 3) There was a 56K sync problem a long time ago. I don't remember who fixed it. (I just tossed the whole driver and re-wrote.) 4) The problem with a bazillion small packets from badly behaved application (no Karn's algorithm, no Nagle algorithm, no Jacobson Slow Start) on an ethernet going into _any_ slower link was posted long ago. 5) I posted a fix in 1991, which simply involves tossing the congested buffers on the slower links. 6) Phil has a different fix in his latest code, which I sure wish he would post. Bill.Simpson@um.cc.umich.edu ------------------------------ Date: Mon, 5 Sep 1994 13:29:37 +0100 From: "Brian A. Lantz" Subject: Linux resolver problem To: A.D.S.Benham@bnr.co.uk On Mon, 5 Sep 1994 A.D.S.Benham@bnr.co.uk wrote: > Is anyone on this list experienced with using the native > Linux TCP/IP facilities? > I've a problem with the resolver. > The DNS I'm using is on the "radio-active" JNOS machine > at home, and the Linux machine is connected to it by an > Ethernet link. > > The problem I have is that the resolver always appends > ".ampr.org" to all its DNS queries, unless the hostname > ends in a dot. > E.g. if I ping "g8iuc" it makes a query for "g8iuc.ampr.org", > if I ping "g8iuc.ampr.org" it makes a query for > "g8iuc.ampr.org.ampr.org", and if I ping "bhl3s1.bnr.co.uk" > it makes query for "bhl3s1.bnr.co.uk.ampr.org". > Only if I specifically add the trailing dot does it work ok. > > Has anyone got a similar setup working correctly by any chance? > > My setup: > > resolv.conf reads > domain ampr.org > nameserver 44.131.181.17 <- the JNOS machine > > hostname = g8fsl > domainname=ampr.org This is the way it is SUPPOSE to work! It is also the way that xNOS works if you have the "domain suffix ampr.org." command in your autoexec.nos file. You see, as far as a DNS is concerned, an Internet domain name ALWAYS ends in a ".", which is the root or base of all names. We are not usually concerned with this, except in the cases that you are seeing. By telling your resolv.conf file that your default domain is "ampr.org", it is going to add that to any name you give it (not in the hosts file) that is NOT terminated with the "." Now the xNOS domain code is NOT as robust or complete as normal DNS code, which will try for a match WITH the default domain, and (if failed) then WITHOUT the default domain. If your name server was a REAL DNS, you would not have to be as restricted. ----------------------------------------------------------- Brian A. Lantz/KO4KS brian@lantz.cftnet.com REAL PORTION of Microsoft Windows code: while (memory_available) { eat_major_portion_of_memory (no_real_reason); if (feel_like_it) make_user_THINK (this_is_an_OS); gates_bank_balance++; } ------------------------------ End of TCP-Group Digest V94 #195 ******************************